-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Handling of low funds cases in the UI (part-2) #568
feat: Handling of low funds cases in the UI (part-2) #568
Conversation
…d integrate with low funds alert
…ok for improved readability and maintainability
…k and remove useChainDetails
{!hasEnoughEthForInitialFunding && ( | ||
<div> | ||
{UNICODE_SYMBOLS.BULLET}{' '} | ||
<Text strong>{nativeTokenRequired}</Text> - for trading. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it's "for trading" only for trader agent I presume. should we have different text based on agent type?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I’m not sure, but I’ll ask Iason/Roman about it.
|
||
const { selectedAgentConfig } = useServices(); | ||
const { evmHomeChainId: homeChainId } = selectedAgentConfig; | ||
const nativeTokenSymbol = getNativeTokenSymbol(homeChainId); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
tiny, could move this to nativeTokenRequired
useMemo
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yup, I will update this in the next PR.
Proposed changes
Design
Changes
Types of changes
What types of changes does your code introduce?
Put an
x
in the boxes that apply